Grid Non-Deterministic Job Scheduling

ABSTRACT

The present invention is method for scheduling jobs in a grid computing environment without having to monitor the state of the resource on the gird comprising a Global Scheduling Program (GSP) and a Local Scheduling Program (LSP). The GSP receives jobs submitted to the grid and distributes the job to the closest resource. The resource then runs the LSP to determine if the resource can execute the job under the conditions specified in the job. The LSP either rejects or accepts the job based on the current state of the resource properties and informs the GSP of the acceptance or rejection. If the job is rejected, the GSP randomly selects another resource to send the job to using a resource table. The resource table contains the state-independent properties of every resource on the grid.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of co-pending US. Utility patent application entitled “Grid Non-Deterministic Job Scheduling” filed on May 20, 2004 and accorded Ser. No. 10/850,387 and claims priority therefrom.

FIELD OF THE INVENTION

The present invention is directed generally to a scheduler for a grid computer network and specifically to a scheduler that does not need to keep track of the real-time state of the properties of each resource on the grid computer network.

BACKGROUND OF THE INVENTION

Recently, companies have begun to explore the possibilities of using grid computing networks (grids) to increase the companies' productivity. A grid comprises a plurality of computers that are networked together. Large or complex computations can be broken up into a plurality of smaller, more manageable jobs (jobs) by the grid. The jobs are then sent out to the computers within the grid for parallel processing. Each job has certain requirements to be executed, such as processor speed, memory, software, execution time, percent utilization, and so forth. The jobs can be routed to the resources depending on their requirements. As the individual computers complete their jobs, the grid reassembles the jobs into the completed result for the computation. The result is that the large or complex computations are processed in significantly less time than is possible on a single computer.

One of the important components of a grid is the scheduler. The scheduler is an algorithm that distributes the individual jobs for processing throughout the grid. The prior art grid schedulers acquire information about the current state of the resource properties on the gird. The information is used to create a real-time picture of the state of the resource properties on the grid. The prior art schedulers examine the real-time information to determine which resource can best execute the job. The prior art schedulers then distribute the job to the resource that can best execute the job. The process is repeated for every job in the grid.

Several problems are associated with the prior art scheduling method. One problem is that the collection of real-time data for the resources consumes a large amount of grid resources. The mechanism by which the scheduler collects and updates the real-time resource data consumes a large amount of network bandwidth between the scheduler and the resources. The mechanism utilizes processor time for the resources and the scheduler computer. Similarly, the mechanism also utilizes large amounts of memory for the resources and the scheduler computer. A scheduler that could reduce or eliminate the data gathering mechanism for the resources could apply the processing time and memory to more beneficial activities. Therefore, a need exists in the art for a scheduler that does not have to know the real-time state of the grid resources in order to distribute jobs to the resources.

Another problem associated with the prior art schedulers is that they are centralized. The prior art schedulers represent a bottleneck in the grid because all of the jobs on the grid must pass through a single computer. The idea behind grid computing is to eliminate the bottlenecks in the computer network by distributing the workload to a plurality of different computers. Decentralization allows the jobs to be completed more quickly than centralized networks. Decentralization is also advantageous because the productivity of the gird is not significantly affected when one of the grid computers goes offline. If the computer containing the prior art scheduler were to go offline, then the grid would have to cease operations until the scheduler came back online. With a decentralized scheduler, the grid would continue to operate when one computer running the scheduler goes offline because the scheduler would be on a plurality of computers. Therefore, a need exits in the art for a scheduler that is located on a plurality of computers on the grid.

SUMMARY OF THE INVENTION

The present invention, which meets the needs identified above, is a method for scheduling jobs in a grid computing environment without having to monitor the state of the resource on the gird. The software embodiment of the present invention comprises a Configuration Program (CP), a Global Scheduling Program (GSP), a Local Scheduling Program (LSP), and an Execution Program (EP). The CP creates and updates a resource table associated with the present invention. The resource table is a record of the state-independent properties of each resource and, therefore, does not contain a record of the current state of the properties of each resource on the grid. Jobs may be submitted anywhere on the grid to the GSP. The GSP receives jobs submitted to the grid and distributes the job to the closest resource. The resource then runs the LSP to determine if the resource can execute the job under the conditions specified in the job. The LSP either rejects or accepts the job based on the current state of the resource properties and informs the GSP of the acceptance or rejection.

If the job is accepted, the LSP places the job in the execution queue for execution by the EP. If the job is rejected, the GSP adds the resource ID to an attempted resources list. The GSP then searches the resource table for resources that have the properties required to execute the job and removes the resources in the attempted resources list from consideration. If any resources remain, then the GSP randomly selects one of the resources and sends the job to that selected resource. If no resources remain, then the GSP determines whether the job has gone through a preset number of iterations. If the job has not gone through a preset number of alterations, then the GSP enters a new iteration by sending the job to the resources in random order until a resource accepts the job or all the resources deny the job. If the job has gone through a preset number of iterations, the job is returned to the originator because the grid was unable to execute the job given the constraints specified in the job. Thus, the present invention is able to schedule jobs for a grid computing network without having to monitor the current state of the properties of each resource within the grid.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 is an illustration of a computer network used to implement the present invention;

FIG. 2 is an illustration of a scheduling computer, including a memory and a processor, associated with the present invention;

FIG. 3 is an illustration of a resource computer, including a memory and a processor, associated with the present invention;

FIG. 4 is an illustration of the logic of the Configuration Program (CP) of the present invention;

FIG. 5 is an illustration of the Resource Table of the present invention;

FIG. 6 is an illustration of the logic of the Global Scheduling Program (GSP) of the present invention;

FIG. 7 is an illustration of the Attempted Resources List of the present invention;

FIG. 8 is an illustration of Local Scheduling Program (LSP) of the present invention;

FIG. 9 is an illustration of the Execution Queue of the present invention; and

FIG. 10 is an illustration of the Execution Program (EP) of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As used herein, the term “accept” shall mean for a resource to have sufficient processing capability, memory, and other attributes to execute a job and for the resource to agree to execute a job.

As used herein, the term “analyze” shall mean to examine a resource and the resource properties.

As used herein, the term “attempted resources list” shall mean a list of resources that have rejected a job.

As used herein, the term “computer” shall mean a machine having a processor, a memory, and an operating system, capable of interaction with a user or other computer, and shall include without limitation desktop computers, notebook computers, personal digital assistants (PDAs), servers, handheld computers, tablet computers, and similar devices.

As used herein, the term “execute” shall mean to process a job into a finished result.

As used herein, the term “execution queue” shall mean a list of jobs that are awaiting execution at a single resource.

As used herein, the term “grid” shall mean a distributed computer network in which a processing task is broken up into a plurality of jobs, the jobs are executed by a plurality of computers, and the executed jobs are reassembled into a finished product.

As used herein, the term “job” shall mean a portion of a grid processing task which needs to be executed by a single resource.

As used herein, the term “reject” shall mean for a resource to decline acceptance of a job because the resource cannot execute the job within the parameters specified by the job.

As used herein, the term “resource” shall mean a computer on a grid that executes a job.

As used herein, the term “resource properties” shall mean the state-independent characteristics of a resource. Examples of resource properties include the resource processor speed, the amount of memory installed in the resource, the software installed on the resource, the resource IP address, the resource physical location, the resource logical location, the resource operating system, and the type of computer that the resource is.

As used herein, the term “resource table” shall mean a table that lists all of the resources on the grid and a plurality of resource properties associated with each resource.

As used herein, the term “scheduler” shall mean a computer algorithm for determining the distribution of pieces of a job in a grid.

As used herein, the term “state dependent” shall mean a characteristic in which the capacity of a resource property changes with time. State dependent properties include wait time, available processing power, current usage, and available memory.

As used herein, the term “state independent” shall mean a characteristic in which the capacity of a resource property does not change with time. State independent properties include processor power and total memory.

FIG. 1 is an illustration of computer network 90 associated with the present invention. Computer network 90 comprises local computer 95 electrically coupled to network 96. Local computer 95 is electrically coupled to remote computer 94 and remote computer 93 via network 96. Local computer 95 is also electrically coupled to server 91 and database 92 via network 96. Network 96 may be a simplified network connection such as a local area network (LAN) or may be a larger network such as a wide area network (WAN) or the Internet. Furthermore, computer network 90 depicted in FIG. 1 is intended as a representation of a possible operating network containing the present invention and is not meant as an architectural limitation.

The internal configuration of a computer, including connection and orientation of the processor, memory, and input/output devices, is well known in the art. The present invention is a methodology that can be embodied in a computer program. Referring to FIG. 2, the methodology of the present invention is implemented on software by Configuration Program (CP) 200 and Global Scheduling Program (GSP) 300. CP 200 and GSP 300 described herein can be stored within the memory of any computer depicted in FIG. 1. Alternatively, CP 200 and GSP 300 can be stored in an external storage device such as a removable disk, a CD-ROM, or a USB storage device. Memory 100 is illustrative of the memory within one of the computers of FIG. 1. Memory 100 also contains Resource Table 120 and Attempted Resources List 140. The present invention may interface with Resource Table 120 and Attempted Resources List 140 through memory 100. As part of the present invention, the memory 100 can be configured with CP 200 and GSP 300. Processor 106 can execute the instructions contained in CP 200 and GSP 300. Processor 106 can communicate with other computers via network 96 using a protocol determined by a person of ordinary skill in the art, such as TCP/IP. Processor 106 and memory 100 are part of a computer such as server 91 in FIG. 1. Server 91 is a computer that schedules a job to a resource when the job is submitted to the grid. CP 200 and GSP 300 can be optionally located on a resource computer if a person of ordinary skill in the art desires further decentralization of the scheduling process. However, locating CP 200 and GSP 300 on a central computer is advantageous because only one copy of CP 200 and GSP 300 would need to be updated. Server 91 may also contain LSP 400 (See FIG. 3), EP 500 (See FIG. 3), and Execution Queue 160 (See FIG. 3) if server 91 is a resource on the grid.

Resource Table 120 is a table of the resources available on the grid containing state-less resource properties that do not change with time. Examples of time-dependent resource properties include available memory, wait time until job is processed, and so forth. Thus, once a resource is added to Resource Table 120, the properties of the resource are not changed within Resource Table 120 unless there is a permanent change in the resource properties. An example of Resource Table 120 is illustrated in FIG. 5. Attempted Resource List 140 is a list of the jobs and the resources that rejected the jobs. An example of Attempted Resource List 140 is illustrated in FIG. 7.

In alternative embodiments, CP 200 and GSP 300 can be stored in the memory of other computers. Storing CP 200 and GSP 300 in the memory of other computers allows the processor workload to be distributed across a plurality of processors instead of a single processor. Further configurations of CP 200 and GSP 300 across various memories are known by persons of ordinary skill in the art. The present invention may be a method, a stand alone computer program, or a plug-in to an existing computer program. Persons of ordinary skill in the art are aware of how to configure computer programs, such as those described herein, to plug into an existing computer program.

Referring to FIG. 2, the methodology of the present invention is also implemented on software by Local Scheduling Program (LSP) 400 and Execution Program (EP) 500. LSP 400 and EP 500 described herein can be stored within the memory of any computer depicted in FIG. 1. Alternatively, LSP 400 and EP 500 can be stored in an external storage device such as a removable disk, a CD-ROM, or a USB storage device. Memory 150 is illustrative of the memory within one of the computers of FIG. 1. Memory 150 also contains Execution Queue 160. The present invention may interface with Execution Queue 160 through memory 150. As part of the present invention, the memory 150 can be configured with LSP 400 and EP 500. Processor 156 can execute the instructions contained in LSP 400 and EP 500. Processor 156 and memory 150 are part of a computer such as local computer 95 in FIG. 1. LSP 400 and EP 500 are located on every resource on the grid, including local computer 95. Processor 156 can communicate with other computers via network 96 using a protocol determined by a person of ordinary skill in the art, such as TCP/IP.

Execution Queue 160 is a list of jobs that need to be executed on local computer 95. Execution Queue 160 also contains a list of the approximate wait time for each job. Each of the computers on the grid contains an Execution Queue 160. An example of Execution Queue 160 is illustrated in FIG. 9.

In alternative embodiments, LSP 400 and EP 500 can be stored in the memory of other computers. Storing LSP 400 and EP 500 in the memory of other computers allows the processor workload to be distributed across a plurality of processors instead of a single processor. Further configurations of LSP 400 and EP 500 across various memories are known by persons of ordinary skill in the art. The present invention may be a method, a stand alone computer program, or a plug-in to an existing computer program. Persons of ordinary skill in the art are aware of how to configure computer programs, such as those described herein, to plug into an existing computer program.

FIG. 4 is an illustration of the logic of Configuration Program (CP) 200 of the present invention. CP 200 is a program that updates the resource table of the present invention. The resource table may be like Resource Table 120 depicted in FIG. 2. CP 200 starts (202) whenever a resource is added to the grid. CP 200 may also start when one of the state independent properties of a resource is changed (i.e. by physical addition of memory to a resource). CP 200 determines whether there are any unanalyzed resources (204). For the purposes of the present invention, a resource has not been analyzed if it is not present in the resource table or the properties of the resource have changed since the resource was added to the resource table. If there are unanalyzed resources, then CP 200 analyzes the next resource (206). In analyzing the next. resource, CP 200 randomly selects one of the unanalyzed resources and determines the properties of the selected resource. CP 200 then adds the resource properties to the resource table (208) and returns to step 204. If at step 204 all of the resources have been analyzed, then CP 200 ends (210).

FIG. 5 is an illustration of Resource Table 120 of the present invention. Resource Table 120 is a table that lists the properties associated with each of the resources on the grid. The resource properties do not normally change with time and are, therefore, state-independent. Resource Table 120 contains resource ID 122, processor speed 124, memory 126, and operating system 128. Resource Table 120 may include the resource's IP address, the physical location of the resource, the logical location of the resource, and the computer type for the resource. Resource Table 120 may also include a description of the individual software applications present on each resource. Persons of ordinary skill in the art are aware of other fields that Resource Table 120 may contain.

FIG. 6 is an illustration of the logic of Global Scheduling Program (GSP) 300. GSP 300 is a program that controls the routing of jobs to resources. GSP 300 starts (302) when the grid comes online. GSP 300 receives notification that a job has been submitted to the grid (304). The job may be submitted on any computer connected to the gird. GSP 300 then determines whether the computer submitting the job is a resource (306). A resource is a computer on the grid that can execute a job. Jobs can be submitted by non-resource computers that are not permanently connected to the grid such as laptops and computers using a dial-up connection. If GSP 300 determines that the submitting computer is a resource, then GSP 300 proceeds to step 310. If GSP 300 determines that the submitting computer is a resource, then GSP 300 sends the job to the resource that is closest in proximity to the submitting computer (308). GSP 300 then waits for the resource with the job to run LSP 400 (310). When the resource responds after running LSP 400, GSP 300 proceeds to step 312.

At step 312, GSP 300 determines whether the resource accepted the job (312). If the resource accepted the job, the GSP 300 proceeds to step 334. If the resource rejected the job, then GSP 300 adds the resource ID and job ID to the attempted resources list (314). The attempted resources list may be like Attempted Resources List 140 depicted in FIGS. 2 and 7. GSP 300 then determines which resources are capable of executing the job (316). Each job has certain requirements as to the resource properties such as processor speed, memory, operating system, required software, as so forth. In determining which resources are capable of executing the job, GSP 300 looks to the resource table and eliminates from consideration the resources that lack sufficient resources to execute the job. The resource table may be like Resource Table 120 depicted in FIGS. 2 and 5. GSP 300 also eliminates from consideration the resources that are on the attempted resources list (318). GSP 300 then proceeds to step 320.

At step 320, GSP 300 determines whether there are any resources remaining after the resources with insufficient properties and the resource on the attempted resources list have been removed from consideration (320). If there are not any resources remaining, then GSP 300 proceeds to step 326. If there are resources remaining, then GSP 300 randomly selects one of the resources from the remaining resource (322). GSP 300 then sends the job to the selected resource (324) and returns to step 310.

At step 326, GSP 300 determines whether the preset number of iterations has been reached (326). When a job is submitted to the grid, the originator includes a preset number of times that the grid tries to execute the job and a wait time between tries before the job is returned to the submitting computer. Each iteration represents an attempt by every qualified resource on the grid to execute the job as specified. If the present number of iterations has not been reached, then GSP 300 clears the attempted resources list for the job (328). GSP 300 then waits for an amount of time specified by the job originator (330) and returns to step 316. Returning to step 326, if the present number of iterations has been reached, then GSP 300 notifies the originator that the job has failed (332). GSP 300 then clears the attempted resources list for the present job (334) and ends (336).

FIG. 7 is an illustration of Attempted Resources List 140. Attempted Resources List 140 is a list of all of the jobs pending on the grid that have not been accepted and the resources that have rejected the jobs. Attempted Resources List 140 comprises job ID 142 and resource ID 144. Persons of ordinary skill in the art are aware of other fields that Attempted Resources List 140 may contain.

FIG. 8 is an illustration of the logic of Local Scheduling Program (LSP) 400. LSP 400 is a program that runs on the resource and determines if the current resource workload will allow the resource to execute the job. LSP 400 starts (402) whenever the resource is online with the grid. LSP 400 receives the job from GSP 300 (404). LSP 400 then determines if the resource can execute the job (406). Each job has certain requirements to be executed, such as processor speed, memory, software, execution time, percent utilization, and so forth. A specific resource may have sufficient processing speed, memory, and software to execute a job, but may have too many other jobs queued to execute the present job in the specified execution time. Alternatively, a resource may have sufficient properties to execute the job but may not have a low enough percent utilization to execute the job. Therefore, in order to determine if the resource can execute the job, LSP examines the resource properties as well as the execution queue. The execution queue may be like Execution Queue 160 depicted in FIGS. 3 and 9.

If at step 406, LSP 400 determines that the resource can execute the job, then LSP 400 indicates to GSP 300 that the resource has been accepted (408). LSP 400 then places the job in the execution queue (410) and ends (416). If at step 406, LSP 400 determines that the resource cannot execute the job, then LSP 400 rejects the job, indicating to GSP 300 that the resource is busy (412). LSP 400 then returns the job to GSP 300 (414) and ends (416).

FIG. 9 is an illustration of Execution Queue 160 associated with the local resource. Execution Queue 160 is an ordered list of job IDs 162 and the approximate waiting time 164 until each job is executed. Persons of ordinary skill in the art are aware of other fields that Execution Queue 160 may contain.

FIG. 10 is an illustration of the logic of Execution Program (EP) 500. EP 500 is a program that runs on the resource and executes the jobs. EP 500 starts (502) whenever the resource is online with the grid. EP 500 receives a job into the execution queue (504). The execution queue may be like Execution Queue 160 depicted in FIGS. 3 and 9. EP 500 executes the next job in the execution queue (506). EP 500 then sends the result of the executed job back to the originator or other destination as specified in the job (508). EP 500 then determines if there are any jobs remaining in the execution queue (510). If there are jobs remaining in the execution queue, then EP 500 returns to step 506. If there are not any jobs remaining in the execution queue, then EP 500 ends (512).

While the present invention is described in terms of a Global Scheduling Program (GSP) and a Local Scheduling Program (LSP), persons of ordinary skill in the art will appreciate that an alternative embodiment of the present invention allows the grid scheduler to be completely decentralized. The present invention can be completely decentralized by installing a GSP and LSP on each resource and running the GSP for each individual job. A person of ordinary skill in the art could optionally combine the GSP and the LSP into a single program and run that program on each job submitted to the grid. In the present embodiment, the loss of a single resource would not significantly decrease the ability of any other resource to accept jobs into the grid or schedule the execution of jobs on the grid. Thus, the present embodiment represents a completely decentralized embodiment of the present invention.

With respect to the above description, it is to be realized that the optimum dimensional relationships for the parts of the invention, to include variations in size, materials, shape, form, function, manner of operation, assembly, and use are deemed readily apparent and obvious to one of ordinary skill in the art. The present invention encompasses all equivalent relationships to those illustrated in the drawings and described in the specification. The novel spirit of the present invention is still embodied by reordering or deleting some of the steps contained in this disclosure. The spirit of the invention is not meant to be limited in any way except by proper construction of the following claims. 

1. A method for scheduling a job on a grid wherein a scheduler does not have to keep track of a plurality of state dependent resource properties.
 2. The method of claim 1 comprising first steps comprising: running a local scheduling program at a resource with the job; determining whether the resource accepted the job; responsive to the determination that the resource did not accept the job, performing second steps comprising: randomly selecting a second resource from a plurality of remaining resources; and sending the job to the second resource and repeating the steps in claim
 2. 3. The method of claim 2 wherein the first steps further comprise: receiving notification that the job has been submitted to the grid.
 4. The method of claim 3 wherein the first steps further comprise: determining whether a submitting computer is the resource; and responsive to the determination that the submitting computer is not the resource, sending the job to the closest resource to the submitting computer.
 5. The method of claim 4 wherein the second steps further comprise: adding the resource to an attempted resources list.
 6. The method of claim 5 wherein the second steps further comprise: determining the remaining resources capable of executing the job using a resource table; removing from consideration the resource on the attempted resources list; determining if any remaining resources remain after removing from consideration the resource on the attempted resources list; and responsive to the determination that remaining resources remain, performing the randomly selecting a second resource from a plurality of remaining resources step.
 7. The method of claim 6 wherein the second steps further comprise: responsive to the determination that remaining resources remain, determining if a preset number of iterations have been reached; responsive to the determination that the preset number of iterations have been reached, clearing the attempted resources list and waiting a specified amount of time; and responsive to the determination that the preset number of iterations have been reached, repeating the steps in claim
 6. 8. The method of claim 7 wherein the second steps further comprise: responsive to the determination that the preset number of iterations have not been reached, notifying an originating computer that the job has failed.
 9. The method of claim 8 wherein the resource table consists of a plurality of state independent resource properties.
 10. The method of claim 9 wherein the local scheduling program comprises: determining whether the resource can execute the job; responsive to the determination that the resource can execute the job, indicating that the resource has accepted the job; and executing the job at the resource.
 11. The method of claim 10 wherein the local scheduling program further comprises: responsive to the determination that the resource cannot execute the job, indicating that the resource has not accepted the job.
 12. The method of claim 11 wherein the job is placed in an execution queue prior to being executed.
 13. The method of claim 12 wherein the local scheduling program determines whether the resource can execute the job by examining the state dependent resource properties.
 14. The method of claim 13 wherein any computer connected to the grid can accept the job.
 15. The method of claim 14 wherein any computer connected to the grid can schedule the job.
 16. A method for scheduling a job on a grid wherein a resource determines whether to accept the job, the method comprising: determining whether the resource can execute the job; responsive to the determination that the resource can execute the job, indicating that the resource has accepted the job; and executing the job at the resource.
 17. The method of claim 16 further comprising: responsive to the determination that the resource cannot execute the job, indicating that the resource has not accepted the job.
 18. The method of claim 17 wherein the job is placed in an execution queue prior to being executed.
 19. The method of claim 18 wherein the resource determines whether the resource can execute the job by examining a plurality of state dependent resource properties.
 20. The method of claim 19 wherein a scheduler does not have to keep track of the state dependent resource properties.
 21. The method of claim 20 further comprising: determining whether the resource accepted the job; responsive to the determination that the resource did not accept the job, performing additional steps comprising: randomly selecting a second resource from a plurality of remaining resources; and sending the job to the second resource and repeating the steps in claim
 16. 22. The method of claim 21 further comprising: receiving notification that the job has been submitted to the grid.
 23. The method of claim 22 further comprising: determining whether a submitting computer is the resource; and responsive to the determination that the submitting computer is not the resource, sending the job to the closest resource to the submitting computer.
 24. The method of claim 23 wherein the additional steps further comprise: adding the resource to an attempted resources list.
 25. The method of claim 24 wherein the additional steps further comprise: determining the remaining resources capable of executing the job using a resource table; removing from consideration the resource on the attempted resources list; determining if any remaining resources remain after removing from consideration the resource on the attempted resources list; and responsive to the determination that remaining resources remain, performing the randomly selecting a second resource from a plurality of remaining resources step.
 26. The method of claim 25 wherein the additional steps further comprise: responsive to the determination that remaining resources remain, determining if a preset number of iterations have been reached; responsive to the determination that the preset number of iterations have been reached, clearing the attempted resources list and waiting a specified amount of time; and responsive to the determination that the preset number of iterations have been reached, repeating the steps in claim
 25. 27. The method of claim 26 wherein the additional steps further comprise: responsive to the determination that the preset number of iterations have not been reached, notifying an originating computer that the job has failed.
 28. The method of claim 27 wherein the resource table consists of a plurality of state independent resource properties.
 29. The method of claim 28 wherein any computer connected to the grid can accept the job.
 30. The method of claim 29 wherein any computer connected to the grid can schedule the job.
 31. A program product for scheduling a job on a grid wherein a scheduler does not have to keep track of a plurality of state dependent resource properties, the program product comprising: a memory; wherein the memory contains instructions for a processor to implement first steps comprising: running a local scheduling program at a resource with the job; determining whether the resource accepted the job; responsive to the determination that the resource did not accept the job, the processor implements second steps comprising: randomly selecting a second resource from a plurality of remaining resources; and sending the job to the second resource and repeating the steps in claim
 31. 32. The program product of claim 31 wherein the first steps further comprise: receiving notification that the job has been submitted to the grid.
 33. The program product of claim 31 wherein the first steps further comprise: determining whether a submitting computer is the resource; and responsive to the determination that the submitting computer is not the resource, sending the job to the closest resource to the submitting computer.
 34. The program product of claim 31 wherein the second steps further comprise: adding the resource to an attempted resources list.
 35. The program product of claim 31 wherein the second steps further comprise: determining the remaining resources capable of executing the job using a resource table; removing from consideration the resource on the attempted resources list; determining if any remaining resources remain after removing from consideration the resource on the attempted resources list; and responsive to the determination that remaining resources remain, performing the randomly selecting a second resource from a plurality of remaining resources step.
 36. The program product of claim 31 wherein the second steps further comprise: responsive to the determination that remaining resources remain, determining if a preset number of iterations have been reached; responsive to the determination that the preset number of iterations have been reached, clearing the attempted resources list and waiting a specified amount of time; and responsive to the determination that the preset number of iterations have been reached, repeating the steps in claim
 31. 37. The program product of claim 31 wherein the second steps further comprise: responsive to the determination that the preset number of iterations have not been reached, notifying an originating computer that the job has failed.
 38. The program product of claim 31 wherein the resource table consists of a plurality of state independent resource properties.
 39. The program product of claim 31 wherein the local scheduling program comprises: determining whether the resource can execute the job; responsive to the determination that the resource can execute the job, indicating that the resource has accepted the job; and executing the job at the resource.
 40. The program product of claim 31 wherein the local scheduling program further comprises: responsive to the determination that the resource cannot execute the job, indicating that the resource has not accepted the job.
 41. The program product of claim 31 wherein the job is placed in an execution queue prior to being executed.
 42. The program product of claim 31 wherein the local scheduling program determines whether the resource can execute the job by examining the state dependent resource properties.
 43. The program product of claim 31 wherein any computer connected to the grid can accept the job.
 44. The program product of claim 31 wherein any computer connected to the grid can schedule the job.
 45. A program product for scheduling a job on a grid wherein a resource determines whether to accept the job, the program product comprising: a memory; wherein the memory contains instructions for a processor to implement steps comprising: determining whether the resource can execute the job; responsive to the determination that the resource can execute the job, indicating that the resource has accepted the job; and executing the job at the resource.
 46. The program product of claim 45 wherein the steps further comprise: responsive to the determination that the resource cannot execute the job, indicating that the resource has not accepted the job.
 47. The program product of claim 45 wherein the job is placed in an execution queue prior to being executed.
 48. The program product of claim 45 wherein the resource determines whether the resource can execute the job by examining a plurality of state dependent resource properties.
 49. The program product of claim 45 wherein a scheduler does not have to keep track of the state dependent resource properties.
 50. The program product of claim 45 wherein the steps further comprise: determining whether the resource accepted the job; responsive to the determination that the resource did not accept the job, performing additional steps comprising: randomly selecting a second resource from a plurality of remaining resources; and sending the job to the second resource and repeating the steps in claim
 45. 51. The program product of claim 45 wherein the steps further comprise: receiving notification that the job has been submitted to the grid.
 52. The program product of claim 45 wherein the steps further comprise: determining whether a submitting computer is the resource; and responsive to the determination that the submitting computer is not the resource, sending the job to the closest resource to the submitting computer.
 53. The program product of claim 50 wherein the additional steps further comprise: adding the resource to an attempted resources list.
 54. The program product of claim 50 wherein the additional steps further comprise: determining the remaining resources capable of executing the job using a resource table; removing from consideration the resource on the attempted resources list; determining if any remaining resources remain after removing from consideration the resource on the attempted resources list; and responsive to the determination that remaining resources remain, performing the randomly selecting a second resource from a plurality of remaining resources step.
 55. The program product of claim 50 wherein the additional steps further comprise: responsive to the determination that remaining resources remain, determining if a preset number of iterations have been reached; responsive to the determination that the preset number of iterations have been reached, clearing the attempted resources list and waiting a specified amount of time; and responsive to the determination that the preset number of iterations have been reached, repeating the steps in claim
 50. 56. The program product of claim 50 wherein the additional steps further comprise: responsive to the determination that the preset number of iterations have not been reached, notifying an originating computer that the job has failed.
 57. The program product of claim 50 wherein the resource table consists of a plurality of state independent resource properties.
 58. The program product of claim 44 wherein any computer connected to the grid can accept the job.
 59. The program product of claim 44 wherein any computer connected to the grid can schedule the job.
 60. An apparatus for scheduling a job on a grid wherein a scheduler does not have to keep track of a plurality of state dependent resource properties, the apparatus comprising: means for receiving notification that the job has been submitted to the grid; means for determining whether a submitting computer is a resource; responsive to the determination that the submitting computer is not the resource, means for sending the job to the closest resource to the submitting computer; means for running a local scheduling program at the resource with the job; means for determining whether the resource accepted the job; responsive to the determination that the resource did not accept the job, means for performing second steps comprising: adding the resource to an attempted resources list; determining the remaining resources capable of executing the job using a resource table; removing from consideration the resource on the attempted resources list; determining if any remaining resources remain after removing from consideration the resource on the attempted resources list; responsive to the determination that remaining resources remain, determining if a preset number of iterations have been reached; responsive to the determination that the preset number of iterations have been reached, clearing the attempted resources list and waiting a specified amount of time; responsive to the determination that the preset number of iterations have been reached, repeating the steps above; responsive to the determination that the preset number of iterations have not been reached, notifying an originating computer that the job has failed; responsive to the determination that remaining resources remain, performing the randomly selecting a second resource from a plurality of remaining resources step; sending the job to the second resource and repeating the steps above; wherein the resource table consists of a plurality of state independent resource properties. wherein the local scheduling program comprises: means for determining whether the resource can execute the job; responsive to the determination that the resource can execute the job, means for indicating that the resource has accepted the job; means for executing the job at the resource; responsive to the determination that the resource cannot execute the job, means for indicating that the resource has not accepted the job; wherein the job is placed in an execution queue prior to being executed; wherein the local scheduling program determines whether the resource can execute the job by examining the state dependent resource properties; wherein any computer connected to the grid can accept the job; and wherein any computer connected to the grid can schedule the job. 